Version Packages#71
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
f28ea99 to
669fa2a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@web-widget/shared-cache@1.9.0
Minor Changes
e7a9731: Fix 304 revalidation persistence so background revalidation with
304 Not Modifiedstores the revalidated policy instead of rebuilding from stale response headers (restores freshHITon subsequent requests).Add
UPDATINGcache status forstale-while-revalidate(aligns with Cloudflare CDN semantics;STALEis reserved forstale-if-error).Return
304 Not ModifiedfromCache.match()when conditional request headers (If-None-Match,If-Modified-Since) match a fresh cached entry.Percent-encode
x-cache-keyheader values so cache keys with control characters or non-Latin-1 Unicode are valid HTTP header field values.Strip persisted
Agefrom stored policy metadata on read for compatibility with entries written before the revalidation fix.2aeb468: Add middleware-friendly
resolveWithCacheandcreateCacheHandlerAPIs with phase-aware origin error handling.